Methods and apparatus for navigating an autonomous vehicle based on a map updated in regions

ABSTRACT

In an embodiment, a method comprises detecting, at a processor of an autonomous vehicle, a discrepancy between a map and a property sensed by at least one sensor onboard the autonomous vehicle, the property being associated with an external environment of the autonomous vehicle. In response to detecting the discrepancy, and based on the discrepancy, an annotation for the map is generated via the processor. A signal representing the annotation is caused to be transmit to a compute device that is remote from the autonomous vehicle. A signal representing a map update is received from the compute device that is remote form the autonomous vehicle. The map update is generated based on the annotation, the map update (1) including replacement information for a region of the map associated with the annotation, and (2) not including replacement information for a remainder of the map.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/678,436, filed on Feb. 23, 2022 and entitled “METHODS AND APPARATUSFOR NAVIGATING AN AUTONOMOUS VEHICLE BASED ON A MAP UPDATED IN REGIONS”,which is incorporated in its entirety herein by reference.

FIELD

In one or more embodiments, an autonomous vehicle is navigated based ona map, where only regions of the map associated with a discrepancy areupdated, and other regions of the map not associated with thediscrepancy are not updated.

BACKGROUND

Vehicles, such as autonomous vehicles, may rely on maps for navigating.Maps can become out of date, however, as topographies change (e.g., newroads built). One method to update a map is to send a mapping vehicle toan area that is to be updated. Data collected by the mapping vehicle canbe used to publish updated maps (e.g., every month, every quarter). Sucha technique, however, can be slow and often updates the entire map,including portions of the map that are not out of date.

SUMMARY

In some implementations, a method comprises receiving, at a processor, asignal representing an indication of a sensed property. The sensedproperty is associated with an external environment of an autonomousvehicle, and the sensed property is sensed by at least one sensoronboard the autonomous vehicle during operation of the autonomousvehicle within the external environment. A map region to be updated isidentified based on the indication of the sensed property. The mapregion is included within a plurality of map regions of a map. The mapincludes data associated with a plurality of different sensor types, andthe map region to be updated is identified during operation of theautonomous vehicle within the external environment. A signalrepresenting a map update is caused to be transmitted, during operationof the autonomous vehicle within the external environment. The mapupdate includes replacement information for the map region and does notincluding replacement information for any other map region from theplurality of map regions of the map.

In some implementations, a method comprises detecting, at a processor ofan autonomous vehicle, a discrepancy between a map and a property sensedby at least one sensor onboard the autonomous vehicle, the propertybeing associated with an external environment of the autonomous vehicle.In response to detecting the discrepancy, and based on the discrepancy,an annotation for the map is generated via the processor. A signalrepresenting the annotation is caused to be transmitted to a computedevice that is remote from the autonomous vehicle. A signal representinga map update is received from the compute device that is remote form theautonomous vehicle. The map update is generated based on the annotation.The map update (1) includes replacement information for a region of themap associated with the annotation, and (2) does not include replacementinformation for a remainder of the map.

In some implementations, a non-transitory, processor-readable mediumstores processor-executable instructions to cause a processor to detecta difference between (1) sensor data generated by at least one sensoronboard an autonomous vehicle, and (2) a map stored in a memory operablycoupled to the processor. The sensor data is associated with an externalenvironment of the autonomous vehicle. In response to detecting thedifference between the sensor data and the map, an annotation for themap is generated. A first signal representing the annotation is causedto be transmitted to a compute device that is remote from the autonomousvehicle. A second signal representing a map update is received from thecompute device that is remote from the autonomous vehicle. The mapupdate is generated based on the annotation. The map update (1) includesreplacement information for a region of the map associated with theannotation, and (2) does not include replacement information for aremainder of the map. The autonomous vehicle is navigated based on theupdated map.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram of a system for updating a region of a mapassociated with a discrepancy, while not updating other regions of themap not associated with the discrepancy, according to an embodiment.

FIG. 2 shows a flowchart of a method for generating a map update tocause a map region of a map to be updated, according to an embodiment.

FIG. 3 shows a flowchart of a method for receiving a map update based ondetecting a discrepancy, according to an embodiment.

FIG. 4 shows a flowchart of a method for updating a region of a map togenerate an updated map for navigating an autonomous vehicle, accordingto an embodiment.

DETAILED DESCRIPTION

Vehicles, such as semi-autonomous vehicles and fully autonomousvehicles, can rely on maps during navigation. As a result, it can bedesirable for the maps to be accurate and up to date. If, for example, aroad is shut down, under construction or newly constructed, it can bedesirable for the maps to be updated accordingly in a manner that isquick and efficient; otherwise, a vehicle may rely on a map that is outof date.

In that context, the techniques described herein are related todetecting a discrepancy between a region (i.e., portion, subset,section) of a map and an environment of a vehicle, and causing theregion of the map to be updated to account for the discrepancy. In someimplementations, circuitry of an autonomous vehicle may determine adiscrepancy between a particular map region of a map (that includesmultiple map regions) and a property of an environment the autonomousvehicle is travelling in. For example, the property may be the presenceof a new road or building, and the discrepancy may be that the new roador building is not included in the map. In response, the circuitry ofthe autonomous vehicle can indicate such a discrepancy by generating anannotation for the map, where the annotation can include enoughinformation such that the map region of the locally-store map is updatedto account for the discrepancy (e.g., location of new road, number oflanes in the new road, size of new building, etc.). The annotation canthen be sent to a remote compute device to generate a software patch(i.e., map update). Thereafter, the map update can be sent from theremote compute device to the autonomous vehicle and/or other autonomousvehicles for updating the map region of the map included in eachautonomous vehicle without having to update other regions of the map notassociated with the discrepancy.

The techniques described herein can provide several advantages. Forexample, only the region of the map associated with the discrepancy(referred to as “map region”) is updated, while other regions of the mapnot associated with the discrepancy are not updated; this allows updatesto be performed quickly (because the entire map does not need to beupdated) and with reduced amounts of data (because the size of the mapupdate is only for the map region and not the entire map). As a result,the map can be updated for example within hours, even as the vehicle isoperating.

FIG. 1 shows a system for updating a map, according to an embodiment.FIG. 1 includes a vehicle 100 communicably coupled to a compute device114 via a network 128. The vehicle 100 includes a processor 110,sensor(s) 112, and memory 102 storing a software model(s) 104,annotation 106, and map 108. The memory 102, processor 110, andsensor(s) 112 included in the vehicle 100 can be operatively coupled toone another (e.g., via a system bus). The compute device 114 includes aprocessor 124 and memory 116 storing a software model(s) 118 and a mapupdate 120. The memory 116 and processor 124 included in the computedevice 114 can be operatively coupled to one another (e.g., via a systembus).

The network 128 can be any suitable communications network(s) fortransferring data, operating over public and/or private networks. Forexample, the network 128 can include a private network, a VirtualPrivate Network (VPN), a Multiprotocol Label Switching (MPLS) circuit,the Internet, an intranet, a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), a worldwideinteroperability for microwave access network (WiMAX®), an optical fiber(or fiber optic)-based network, a Bluetooth® network, a virtual network,and/or any combination thereof. In some instances, the communicationnetwork 128 can be a wireless network such as, for example, a Wi-Fi orwireless local area network (“WLAN”), a wireless wide area network(“WWAN”), and/or a cellular network. In other instances, thecommunication network 128 can be a wired network such as, for example,an Ethernet network, a digital subscription line (“DSL”) network, abroadband network, and/or a fiber-optic network. The network 128 can bea combination of a wired network(s) and a wireless network(s). In someinstances, the network can use Application Programming Interfaces (APIs)and/or data interchange formats (e.g., Representational State Transfer(REST), JavaScript Object Notation (JSON), Extensible Markup Language(XML), Simple Object Access Protocol (SOAP), and/or Java Message Service(JMS)). The communications sent via the network 128 can be encrypted orunencrypted. In some instances, the network 128 can include multiplenetworks or subnetworks operatively coupled to one another by, forexample, network bridges, routers, switches, gateways and/or the like(not shown in FIG. 1 ).

In some implementations, the vehicle 100 can operate in only a manualdriving mode, only a semi-autonomous driving mode, only a fullyautonomous driving mode, or in a combination thereof (i.e., switchablebetween at least two of the manual driving mode, the semi-autonomousdriving mode, or the fully autonomous driving mode). In someimplementations, the vehicle is at least one of: a semi-truck, a mediumtruck, a heavy truck, a very heavy truck, greater than 14,000 pounds,greater than 26,000 pounds, greater than 70,000 pounds, or greater than80,000 pounds. Having accurate maps can be desirable for larger/heaviervehicles because, for example, accidents caused by larger/heaviervehicles can be more dangerous (e.g., cause more damage) compare tosmaller/lighter vehicles.

The sensor(s) 112 can include one or more sensors for collecting sensordata. The sensor(s) 112 can be used to observe and gather anyinformation that would be useful for performing the techniques discussedherein, such as information associated with an external environment ofthe vehicle 100 and/or the vehicle 100 itself. The sensor(s) 112 caninclude, for example, at least one of an inertial measurement unit(IMU), camera, a radar, or a lidar. The sensor(s) 112 can collect sensordata that includes representations of attributes associated with thevehicle 100, such as the vehicle's 100 speed, location, acceleration,size, weight, etc. Additionally or alternatively, the sensor(s) 112 cancollect sensor data that includes representations of attributesassociated with an external environment of the vehicle 100, such as aspeed, location, acceleration, size, type, relative distance, movementpattern, etc. of other vehicles, pedestrians, animals, obstacles, etc.,and/or location, type, relative distance, size, shape, etc. of signs,lane markers, shoulder areas, roads, buildings, etc. In someimplementations, sensor data collected by the sensor(s) 112 includesinformation of a topography surrounding the vehicle 100 that is relevantfor including in a map, such as a road, sign, traffic light, walkway,building, body of water, etc.

The processor 110 can be, for example, a hardware based integratedcircuit (IC) or any other suitable processing device configured to runand/or execute a set of instructions or code. For example, the processor110 can be a general-purpose processor, a central processing unit (CPU),an accelerated processing unit (APU), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA), a programmablelogic array (PLA), a complex programmable logic device (CPLD), aprogrammable logic controller (PLC) and/or the like. In someimplementations, the processor 110 can be configured to run any of themethods and/or portions of methods discussed herein.

The memory 102 can be, for example, a random-access memory (RAM), amemory buffer, a hard drive, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), and/or the like. The memory 102can be configured to store sensor data collected by the sensor(s) 112,data received from a separate compute device (e.g., compute device 114),and any other data used by the processor 110 to perform the techniquesdiscussed herein. In some instances, the memory 102 can store, forexample, one or more software programs and/or code that can includeinstructions to cause the processor 110 to perform one or moreprocesses, functions, and/or the like. In some implementations, thememory 102 can include extendible storage units that can be added andused incrementally. In some implementations, the memory 102 can be aportable memory (for example, a flash drive, a portable hard disk,and/or the like) that can be operatively coupled to the processor 110.In some instances, the memory 102 can be remotely operatively coupledwith a compute device (not shown). For example, a remote database devicecan serve as a memory and be operatively coupled to the vehicle 100.

The memory 102 stores a representation of a map 108. The map 108includes information that is used and/or could be relevant for thevehicle 100 to navigate, such as information associated with roads,traffic signs, and obstacles (e.g., buildings, barriers). The map 108 ismade up of several regions (i.e., map regions), where each region can beassociated with a logical identifier. In some implementations, thelogical identifiers can be used to identify which map region is to beupdated (discussed in more detail below). The area of land/water makingup the map 108 and map regions can be any shape, such as a square,rectangle, circle, hexagon, irregular shape, etc.

The areas of land and/or water making up the map 108 and map regions canvary. The map 108 can be, for example, a map of a country, state, city,neighborhood, or any other area of land/water. The map regions can beregions that, together, make up the area defining the map 108. Forexample, if the map 108 is of New York City, the map regions can includethe Bronx, Brooklyn, Manhattan, Queens, and Staten Island. As anotherexample, if the map 108 is of Manhattan, the map regions can includeuptown Manhattan, downtown Manhattan, midtown Manhattan, and West Side.As another example, if the map 108 is of midtown Manhattan, the mapregions can include Rockefeller Center, Diamond District, Times Square,Hudson Yards, Koreatown, Madison Square, etc.

The memory 102 also stores a software model(s) 104. The softwaremodel(s) 104 can be, for example, an artificial intelligence (AI)model(s), a machine learning (ML) model(s), an analytical model(s),and/or a mathematical model(s). In some implementations, the softwaremodel(s) 104 can analyze sensor data collected by the sensor(s) 112 todetermine if a discrepancy exists between a sensed property associatedwith the external environment of the vehicle 100 and the map 108. Thesensed property can be any attribute associated with the externalenvironment of the vehicle 100 that may be discrepant with informationincluded in the map 108. For example, the sensed property could be thata road, obstacle, or traffic sign is determined to be present based onsensor data collected by the sensor(s) 112, and the discrepancy could bethat the sensed road, obstacle, or traffic sign is not currently presentin the map 108. As another example, the sensed property could be a road,obstacle, or traffic sign that is determined to be not present based onsensor data collected by the sensor(s) 112, and the discrepancy could bethat the sensed road, obstacle, or traffic sign is currently present inthe map 108. In some implementations, the sensed property is anattribute associated with a road the vehicle 100 is travelling in, suchas a shape of the road, number of lanes in the road, whether a road isavailable (e.g., not closed for construction), angle of the road (e.g.,bank angle, incline angle), name of the road, traffic signs included inthe road, obstacles included in and/or nearby to the road, amount oftraffic in the road, etc.

When a discrepancy is determined by the software model(s) 104 to exist,the software model(s) 104 can generate an annotation 106 (e.g.,automatically without requiring human intervention). The annotation 106can be used to generate a map update 120 for a region of the map 108where the discrepancy was identified, without generating an update forother regions of the map 108 where the discrepancy was not identified.The annotation 106 can indicate the sensed property and/or sensedproperties discrepant with the map 108, as well as any other informationthat would be relevant for ensuring that the sensed property isaccounted for in the map 108. For example, the annotation 106 canindicate the presence of a road connecting from a first location to asecond location, a shape of the road, number of lanes in the road,whether a road is available (e.g., not closed for construction), angleof the road (e.g., bank angle, incline angle), name of the road, trafficsigns included in the road, obstacles included in and/or nearby to theroad, amount of traffic in the road, etc. One or more signalsrepresenting the annotation 106 can then be sent over the network 128 tothe compute device 114. In some implementations, the annotation 106includes an indication of an unsafe condition (e.g., obstacle blockingroad or closed road), which could cause analysis of that annotation 106(i.e., generating the map update 120) to be prioritized.

The compute device 114 can be any type of compute device with aprocessor 124 and memory 116 operatively coupled to the processor 124.The compute device 114 can be, for example, a desktop computer, laptop,table, phone, server, internet-of-things device, etc. In someimplementations, the vehicle 100 is associated with an entity, and thecompute device 114 is associated with the same entity. For example, thevehicle 100 can be a truck operated, designed, and/or owned by PlusAI®,and the compute device 114 can be operated, authorized, accessible,and/or owned by PlusAI®.

The processor 124 can be, for example, a hardware based integratedcircuit (IC) or any other suitable processing device configured to runand/or execute a set of instructions or code. For example, the processor124 can be a general-purpose processor, a central processing unit (CPU),an accelerated processing unit (APU), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA), a programmablelogic array (PLA), a complex programmable logic device (CPLD), aprogrammable logic controller (PLC) and/or the like. In someimplementations, the processor 124 can be configured to run any of themethods and/or portions of methods discussed herein.

The memory 116 can be, for example, a random-access memory (RAM), amemory buffer, a hard drive, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), and/or the like. The memory 116can be configured to store sensor data collected by the sensor(s) 112,data received from a separate compute device (e.g., compute device 114),and any other data used by the processor 124 to perform the techniquesdiscussed herein. In some instances, the memory 116 can store, forexample, one or more software programs and/or code that can includeinstructions to cause the processor 124 to perform one or moreprocesses, functions, and/or the like. In some implementations, thememory 116 can include extendible storage units that can be added andused incrementally. In some implementations, the memory 116 can be aportable memory (for example, a flash drive, a portable hard disk,and/or the like) that can be operatively coupled to the processor 124.In some instances, the memory 116 can be remotely operatively coupledwith a compute device (not shown). For example, a remote database devicecan serve as a memory and be operatively coupled to the compute device114.

The memory 116 can store a software model(s) 118. The software model(s)104 can be, for example, an artificial intelligence (AI) model(s), amachine learning (ML) model(s), an analytical model(s), or amathematical model(s). After the processor 124 has received theannotation 106 from the vehicle 100, the software model(s) 118 can usethe annotation 106 to generate a map update 120 (e.g., software patch).The map update 120 can include information for updating the region ofthe map 108 associated with the discrepancy, and can be sent from thecompute device 114 to the vehicle 100 and/or other vehicles (not shown)operatively coupled to network 128 and configured to receive the mapupdate 120. The map update 120 can be associated with a shape, where theshape represents an area that is the same as the map region that is tobe updated. The map update 120 can also be associated with a logicalidentifier, where the logical identifier identifies the particular mapregion of the map 108 to be updated. In some implementations, the shapeand logical identifier associated with the map update 120 can be thesame as the shape and logical identifier associated with the map regionto be updated.

Once the vehicle 100 (e.g., processor 110) has received the map update120, the software model(s) 104 can use the map update 120 to update themap 108 (e.g., automatically without requiring human input). This cancause the map 108 to be updated (i.e., fixed) to account for thepreviously detected discrepancy. The map region of the map 108 to beupdated can replaced based on the map update 120. This can look for, forexample, associating respective logical identifiers of the map update120 and map region to be updated so that the software model(s) 104 candetermine which map region of the map 108 the map update 120 is toupdate. Thereafter, the shape of the map update 120 can be aligned toand replace the map region to be updated. The aligning can include, forexample, rotating and/or scaling the map update 120 (e.g., to ensurethat roads are accurately aligned, to ensure that the map update 120 hasa correct orientation relative to other regions of the map 108, etc.)

In some implementations, updating the map 108 with the map update 120includes generating, analyzing, verifying, correcting, and/or smoothinga transition region positioned between a portion of the updated map 108associated with the map update 120 and a portion of the updated map 108that is not associated with the map update 120. The transition regioncan be aligned with each portion of the updated map 108 associated withthe map update 108 and each portion of the updated map 108 that is notassociated with the map update 120. The transition region can ensuregeometric consistency and logical consistency (e.g., compensating forglobal positioning system (GPS) errors, lining up lane boundaries, etc.)

This updated map 108 can then be used by the vehicle 100 for navigation.Had the map 108 not been updated using the map update 120, the vehicle100 and/or other vehicle relying on the map 108 may have operated in adifferent manner (e.g., taken a different route that is longer, tried totake a route that does not exist, ignored a traffic sign, not switchedinto a manual driving mode, etc.).

In some implementations, the map 108 is included in the memory 116 ofthe compute device 114 instead of the memory 102 of the vehicle 100. Insuch a scenario, the map update 120 can be used to update the map 108 atthe compute device 114 instead of at the vehicle 100. Other vehicles,which can include vehicle 100, can use the map 108 stored in the memory116 of the compute device 114 for navigation.

In some implementations, the map update 120 can be generated locally inthe vehicle 100 without using the compute device 114. In someimplementations, the software model(s) 104 can perform thefunctionalities of the software model(s) 118, including generating themap update 120 and using the map update 120 to generate an updated map108.

In some implementations, the memory 102 does not include the softwaremodel(s) 104, annotation 106, and map 108. Instead, the functionalitiesof the software model(s) 104 can be performed by the software model(s)118 of the compute device 114, including generating the annotation 106(via sensor data collected by sensor(s) 112 and sent to the computedevice 114) and updating the map 108 using the map update 120.

In some implementations, the map update 120 is sent to other vehicles(not shown), including the vehicle 100, where each vehicle includescopies of the map 108. Each of the vehicles can use the map update 120to update maps stored within their respective memories.

In some implementations, the software model(s) 104 of the vehicle 100can generate the map update 120 locally (using annotation 106) to updatethe map 108. Additionally, the annotation 106 (e.g., a copy) can be sentto the compute device 114 for (1) generating the map update 120 at thecompute device 114, and (2) sending the map update 120 generated at thecompute device 114 to other vehicles (not shown) that do not includevehicle 100.

In some implementations, the map update 120 and/or variations of the mapupdate 120 can be sent to a plurality of vehicles that includes vehicle100. In some implementations, a vehicle closer to a map region that isto be updated can receive a map update with at least enough informationto avoid a dangerous situation (e.g., that a road no longer exists),while a vehicle further away from the map region can receive a mapupdate with more information that may not be necessary to know foravoiding a dangerous situation, but can still be desirable to know(e.g., that a new road has been built). In some implementations, avehicle closer to a map region that to be updated can receive the mapupdate 120 before a different vehicle that is further away from the mapregion that is to be updated.

In some implementations, the map update 120 is sent to a plurality ofvehicles that includes the vehicle 100, based on a priority list. Forinstance, only vehicles included in the priority list receive the mapupdate 120, and vehicles not included in the priority list do notreceive the map update 120, receive the map update 120 later, and/orreceive a different map update different than the map update 120. Thepriority list can include, for example, only vehicles included in themap region to be updated, only vehicles included in the map region to beupdated and map regions adjacent to the map region to be updated, onlyvehicles within a predetermined radius (e.g., 5 miles, 10 miles, 25miles, 50 miles, 100 miles, 250 miles, 500 miles, etc.) of a locationassociated with a discrepancy, only fully autonomous driving vehicles,only semi-autonomous vehicles, only semi-trucks, a combination thereof,etc.

In some implementations, prior to the map update 120 being sent to thevehicle 100, a human (user) verifies, at the compute device 114 and/or adifferent compute device (not shown) communicable coupled to the computedevice 114, that the map update 120 should be sent to the vehicle 100and/or other vehicles. In some implementations, a graphical userinterface (GUI) can be included in the compute device 114 (not shown inFIG. 1 ). A representation of the map update 120 (e.g., shape, logicalidentifier, roads, obstacles, signs, etc.) can be shown to a user viathe GUI, and the user can verify that the map update 120 is accurateand/or properly aligned. After the user verifies that the map update 120is accurate and/or properly aligned, the map update 120 can be sent fromthe compute device 114 to the vehicle 100 and/or other vehicles.

In some implementations, the map update 120 is generated and sent to thevehicle 100 and/or other vehicles automatically without requiring humaninput. In some implementations, the map 108 is updated automatically inresponse to receiving the map update 120. In some implementations, apassenger of the vehicle 100 (e.g., driver) may receive an indication(e.g., notification) that a map update 120 has been received. Further,the passenger can decide if the map 108 should be updated now or later(e.g., at a predetermined time or a time specified by the passenger).

In some implementations, the vehicle 100 is caused to perform at leastone remedial action in response to the software model(s) 104 determiningthat a discrepancy exists. For example, the vehicle 100 can receive asignal (e.g., generated by processor 110) that causes the vehicle 100 tooperate in a manual driving mode or semi-autonomous driving mode untilthe map 108 has been updated with the map update 120. As anotherexample, the vehicle 100 can be prevented from operating in asemi-autonomous and/or fully autonomous driving mode until the map 108has been updated with the map update 120.

In some implementations, the compute device 114 is caused to (e.g.,receives a signal instructing the compute device 114 to) perform atleast one remedial action in response to receiving an annotation 106.For example, the at least one remedial action can be to send a warningsignal to another vehicle(s) that is near (e.g., heading towards) thearea associated with the discrepancy (e.g., to warn a driver of thevehicle, to cause the vehicle to operate in a manual driving mode, tocause the vehicle to gather extra sensor data, etc.).

In some implementations, an indication of the vehicle's 100 locationand/or an estimated location of the discrepancy, such as GPScoordinates, are sent from the vehicle 100 to the compute device 114before, at the same time as, and/or after the annotation 106 is sent.This location indication can allow the compute device 114 to be madeaware of and/or estimate the map region to be updated.

In some implementations, the map update 120 has a file size less than atleast one of: 2 megabytes (MB), 1 MB, 0.5 MB, or 0.25 MB. In someimplementations, the map 108 has a file size greater than at least oneof: 1 gigabyte (GB), 5 GB, 10 GB, 25 GB, 40 GB, 45 GB, 50 GB, 55 GB, or60 GB. In some implementations, the map update 120 has a file size lessthan a file size of the map 108. In some implementations, the map update120 has a file size less than at least one of 1%, 2%, 3%, 5%, 10%, 20%,25%, 50%, or 75% of the map's 108 file size.

In some implementations, the map 108 is updated based on the map update120 to account for a discrepancy within at least one of: one day fromthe software model(s) 104 detecting the discrepancy, four hours from thesoftware model(s) 104 detecting the discrepancy, three hours from thesoftware model(s) 104 detecting the discrepancy, two hours from thesoftware model(s) 104 detecting the discrepancy, or one hour from thesoftware model(s) 104 detecting the discrepancy.

In some implementations, the map update 120 causes a discrete,contiguous area of the map 108 to be replaced. The region of the map 108associated with the discrepancy can be replaced, while other regions ofthe map not associated with the discrepancy are not. For example, if themap 108 is of New York City, the map update 120 can cause Manhattan tobe replaced, while not changing other map regions (e.g., Bronx,Brooklyn, Queens, and Staten Island).

In some implementations, if the vehicle 100 is not able to communicatewith the compute device 114 (e.g., the network 128 is down, circuitryfor communicating in the compute device 114 and/or vehicle 100 is notworking, etc.), the annotation 106 and/or map update 120 can bescheduled for a future transmission (e.g., when the network 128 becomesavailable, circuitry for communicating in the compute device 114 and/orvehicle 100 is working, etc.) to trigger generation of the map update120 (in response to receiving the annotation 106) and/or updated versionof the map 108 (in response to receiving the map update 120).

Although the above discussion relates to updating a map 108 using a mapupdate 120 and an annotation 106, it can be appreciated that any numberof map updates and annotations can be generated for any number of maps.For example, a second annotation (different than annotation 106) can begenerated based on a different sensed property, and a second map update(different than map update 120) can be used to update the map 108 and/ora second map stored in memory 102 of the vehicle 100 that is differentthan map 108.

FIG. 2 shows a flowchart of a method for generating a map update tocause a map region of a map to be updated, according to an embodiment.In some implementations, the method of FIG. 2 can be performed by theprocessor 124 of the compute device 114.

At 202, a signal representing an indication of a sensed property isreceived at a processor (e.g., processor 124). The sensed property isassociated with an external environment of an autonomous vehicle (e.g.,vehicle 100), and the sensed property is sensed by at least one sensor(e.g., sensor(s) 112) onboard the autonomous vehicle during operation(e.g., running and/or moving) of the autonomous vehicle within theexternal environment. In some implementations, the sensed property is atopographical feature, such as a size, location, shape, type, or heightassociated with a topography of the external environment (e.g., road,building, lake, etc.). In some implementations, the sensor propertyindicates a discrepancy compared to an expected topographical feature asindicated by a map (e.g., map 108) used by the autonomous vehicle fornavigation.

At 204, based on the indication of the sensed property, a map region tobe updated is identified. The map region is included within a pluralityof map regions of a map. The map includes data associated with aplurality of different sensor types (e.g., the map created and/ormodified using sensors of different sensor types, such as at least twoof a camera, radar, or lidar), and the identifying occurs duringoperation of the autonomous vehicle within the external environment. Insome implementations, the map region can be identified based on anannotation (e.g., annotation 106) of the map. In some implementations,the annotation can include GPS coordinates, where the GPS coordinatescan indicate an approximate location associated the sensed property. Insome implementations, step 204 can be performed in response tocompleting step 202 automatically and without requiring human input.

At 206, a signal representing a map update (e.g., map update 120) iscaused to be transmitted (e.g., the processor sends an electrical signalto a transmitter and/or transceiver operatively coupled to the processorinstructing the signal representing the map update to be transmitted)during operation of the autonomous vehicle within the externalenvironment. The map update includes replacement information for the mapregion and does not include replacement information for any other mapregion from the plurality of map regions of the map. The signal can besent, for example, to the autonomous vehicle and/or each autonomousvehicle from a plurality of autonomous vehicles (e.g., based on apriority list). In some implementations, step 206 is performedautomatically and without requiring human input in response to the mapupdate being generated.

FIG. 3 shows a flowchart of a method for receiving a map update based ondetecting a discrepancy, according to an embodiment. In someimplementations, the method of FIG. 3 can be performed by the processor110 of the vehicle 100.

At 302, a discrepancy between a map (e.g., map 108) and a propertysensed by at least one sensor (e.g., sensor(s) 112) onboard theautonomous vehicle is detected at a processor (e.g., processor 110) ofan autonomous vehicle (e.g., vehicle 100). The property is associatedwith an external environment of the autonomous vehicle. The property canbe, for example, a topographical feature of the external environment,such as an attribute of a road or obstacle.

At 304, in response to detecting the discrepancy, and based on thediscrepancy, an annotation (e.g., annotation 106) for the map isgenerated via the processor. The annotation can indicate the propertydiscrepant with the map, as well as any other information that would berelevant for ensuring that the property is accounted for in the map(e.g., included and/or removed). In some implementations, the annotationcan be generated automatically without requiring human input in responseto detecting the discrepancy at 302.

At 306, a signal representing the annotation to a compute device (e.g.,compute device 114) that is remote from the autonomous vehicle is causedto be transmitted (e.g., the processor sends an electrical signal to atransmitter and/or transceiver operatively coupled to the processorinstructing the signal representing the annotation to be transmitted).In some implementations, the compute device is owned, operated, and/orauthorized by an entity, and the autonomous vehicle is also owned,operated, and/or authorized by the same entity. In some implementations,the signal can be transmitted without requiring human input in responseto generating the annotation at 304.

At 308, a signal representing a map update (e.g., map update 120) isreceived from the compute device that is remote from the autonomousvehicle. The map update generated based on the annotation (e.g., bysoftware model(s) 118). The map update (1) includes replacementinformation for a region of the map associated with the annotation, and(2) does not include replacement information for a remainder of the map.In some implementations, 308 is performed as the autonomous vehicle 100is operating (e.g., driving).

In some implementations, after performing 308, the map is updated, viathe processor and during operation of the autonomous vehicle, based onthe map update, to generate an updated map. The map can be updated(e.g., by software model(s) 104) in response to receiving the signal at308 automatically and without requiring human input. In someimplementations, the autonomous vehicle is navigated based on theupdated map.

In some implementations, the property at 302 is a first property, and asecond property associated with the external environment of theautonomous vehicle is detected by the at least one sensor in response todetecting the discrepancy. The map update is generated further based onthe second property. The second property can be different than the firstproperty.

FIG. 4 shows a flowchart of a method for updating a region of a map togenerate an updated map for navigating an autonomous vehicle, accordingto an embodiment. In some implementations, the method of FIG. 4 can beperformed by the processor 110 of the vehicle 100.

At 402, a difference is detected between (1) sensor data generated by atleast one sensor (e.g., sensor(s) 112) onboard an autonomous vehicle(e.g., vehicle 100), and (2) a map (e.g., map 108) stored in a memory(memory 102) operably coupled to the processor. The sensor data isassociated with an external environment of the autonomous vehicle. At404, in response to detecting the difference between the sensor data andthe map (e.g., automatically without requiring human input), anannotation (e.g., annotation 106) for the map is detected. Theannotation can be associated with only a map region of the map (i.e.,not the entire map). At 406, a first signal representing the annotationis caused to be transmitted (e.g., the processor sends an electricalsignal to a transmitter and/or transceiver operatively coupled to theprocessor instructing the first signal to be transmitted) to a computedevice (e.g., compute device 114) that is remote from the autonomousvehicle. At 408, a second signal representing a map update (e.g., mapupdate 120) is received from the compute device that is remote from theautonomous vehicle. The map update is generated based on the annotation.The map update (1) includes replacement information for a region of themap associated with the annotation, and (2) does not include replacementinformation for a remainder of the map. At 410, the autonomous vehicleis navigated based on the updated map.

In some implementations, the method of FIG. 4 further includesautomatically causing detection of additional sensor data in response todetecting the difference between the first sensor data and the map. Forinstance, the sensor data at 402 may not include enough information/datato generate the annotation at 404. In such a case, the additional sensordata can be collected. For example, the sensor data at 402 may indicatethat a new road has been constructed, and the additional sensor data canindicate attributes of the new road, such as the new road's approximatelocation, shape, number of lanes, etc. Thereafter, a third signal can betransmitted to the compute device that is remote from the autonomousvehicle, to trigger generation of the map update in response to thedetection of the additional sensor data.

In some implementations, the method of FIG. 4 further includes causingtransmission of a third signal to the compute device that is remote fromthe autonomous vehicle to trigger generation of the map update inresponse to receiving the third signal. In such a case, the first signalsent at 406 does not cause the compute device that is remote from theautonomous vehicle to trigger generation of the map update. The thirdsignal can be sent, for example, when a network connection has astrength above a predetermined threshold, when a network connection isestablished and/or verified to be established, etc.

In an embodiment, a method comprises: receiving, at a processor, asignal representing an indication of a sensed property, the sensedproperty being associated with an external environment of an autonomousvehicle, and the sensed property being sensed by at least one sensoronboard the autonomous vehicle during operation of the autonomousvehicle within the external environment; identifying, based on theindication of the sensed property, a map region to be updated, the mapregion being included within a plurality of map regions of a map, themap including data associated with a plurality of different sensortypes, the identifying occurring during operation of the autonomousvehicle within the external environment; and causing transmission of asignal representing a map update, during operation of the autonomousvehicle within the external environment, the map update includingreplacement information for the map region and not including replacementinformation for any other map region from the plurality of map regionsof the map.

In some implementations, the identifying the map region is based on anannotation of the map, the annotation received from the autonomousvehicle.

In some implementations, the sensed property is a topographical feature.

In some implementations, the map update has a file size of less thanabout 1 megabyte (MB).

In some implementations, the transmission of the signal representing themap update is to the autonomous vehicle.

In some implementations, the transmission of the signal representing themap update is to each autonomous vehicle from a plurality of autonomousvehicles that includes the autonomous vehicle.

In some implementations, the transmission of the signal representing themap update is to each autonomous vehicle from a plurality of autonomousvehicles that includes the autonomous vehicle, and is based on apriority list.

In some implementations, the map update replaces a discrete, contiguousarea of the map.

In an embodiment, a method comprises: detecting, at a processor of anautonomous vehicle, a discrepancy between a map and a property sensed byat least one sensor onboard the autonomous vehicle, the property beingassociated with an external environment of the autonomous vehicle;generating, via the processor, in response to detecting the discrepancy,and based on the discrepancy, an annotation for the map; causingtransmission of a signal representing the annotation to a compute devicethat is remote from the autonomous vehicle; and receiving, from thecompute device that is remote from the autonomous vehicle, a signalrepresenting a map update, the map update generated based on theannotation, the map update (1) including replacement information for aregion of the map associated with the annotation, and (2) not includingreplacement information for a remainder of the map.

Some implementations further comprise: updating the map, via theprocessor and during operation of the autonomous vehicle, based on themap update, to generate an updated map; and navigating the autonomousvehicle based on the updated map.

In some implementations, the updating the map includes: aligning a shapeof the map update with at least a portion of the map; and associating alogical identifier of the map update with a logical identifier of themap.

In some implementations, the updated map includes a transition regionpositioned between a portion of the updated map associated with the mapupdate and a portion of the updated map that is not associated with themap update, the transition region being aligned with each of the portionof the updated map associated with the map update and the portion of theupdated map that is not associated with the map update.

In some implementations, the property is a first property, the methodfurther comprising: detecting, by the at least one sensor onboard theautonomous vehicle, a second property associated with the externalenvironment of the autonomous vehicle, in response to detecting thediscrepancy, the map update generated further based on the secondproperty.

In some implementations, the property is a topographical feature of theexternal environment.

In an embodiment, a non-transitory, processor-readable medium storingprocessor-executable instructions to cause a processor to: detect adifference between (1) sensor data generated by at least one sensoronboard an autonomous vehicle, and (2) a map stored in a memory operablycoupled to the processor, the sensor data being associated with anexternal environment of the autonomous vehicle; generate, in response todetecting the difference between the sensor data and the map, anannotation for the map; cause transmission of a first signalrepresenting the annotation to a compute device that is remote from theautonomous vehicle; receive, from the compute device that is remote fromthe autonomous vehicle, a second signal representing a map update, themap update generated based on the annotation, the map update (1)including replacement information for a region of the map associatedwith the annotation, and (2) not including replacement information for aremainder of the map; and navigate the autonomous vehicle based on theupdated map.

In some implementations, the map update has a file size of less thanabout 1 megabyte (MB).

In some implementations, the map update has a file size that is lessthan a file size of the map.

In some implementations, the sensor data is first sensor data, themedium further storing processor-executable instructions to cause theprocessor to: automatically cause detection of additional sensor data inresponse to detecting the difference between the first sensor data andthe map; and cause transmission of a third signal to the compute devicethat is remote from the autonomous vehicle, to trigger generation of themap update in response to the detection of the additional sensor data.

In some implementations, the non-transitory, processor-readable mediumfurther stores processor-executable instructions to cause the processorto cause transmission of a third signal to the remote compute devicethat is remote from the autonomous vehicle to trigger generation of themap update in response to receiving the third signal.

In some implementations, the non-transitory, processor-readable mediumfurther stores processor-executable instructions to cause the processorto: in response to detecting that a communications network isunavailable, schedule a future transmission of a third signal to aremote compute device to trigger generation of the map update inresponse to receiving the third signal.

In some implementations, the annotation includes an indication of anunsafe condition.

In some implementations, the generation of the map update includes:aligning a shape of the map update with at least a portion of the map;and associating a logical identifier of the map update with a logicalidentifier of the map.

All combinations of the foregoing concepts and additional conceptsdiscussed here (provided such concepts are not mutually inconsistent)are contemplated as being part of the subject matter disclosed herein.The terminology explicitly employed herein that also may appear in anydisclosure incorporated by reference should be accorded a meaning mostconsistent with the particular concepts disclosed herein.

The skilled artisan will understand that the drawings primarily are forillustrative purposes, and are not intended to limit the scope of thesubject matter described herein. The drawings are not necessarily toscale; in some instances, various aspects of the subject matterdisclosed herein may be shown exaggerated or enlarged in the drawings tofacilitate an understanding of different features. In the drawings, likereference characters generally refer to like features (e.g.,functionally similar and/or structurally similar elements).

To address various issues and advance the art, the entirety of thisapplication (including the Cover Page, Title, Headings, Background,Summary, Brief Description of the Drawings, Detailed Description,Embodiments, Abstract, Figures, Appendices, and otherwise) shows, by wayof illustration, various embodiments in which the embodiments may bepracticed. The advantages and features of the application are of arepresentative sample of embodiments only, and are not exhaustive and/orexclusive. Rather, they are presented to assist in understanding andteach the embodiments, and are not representative of all embodiments. Assuch, certain aspects of the disclosure have not been discussed herein.That alternate embodiments may not have been presented for a specificportion of the innovations or that further undescribed alternateembodiments may be available for a portion is not to be considered toexclude such alternate embodiments from the scope of the disclosure. Itwill be appreciated that many of those undescribed embodimentsincorporate the same principles of the innovations and others areequivalent. Thus, it is to be understood that other embodiments may beutilized and functional, logical, operational, organizational,structural and/or topological modifications may be made withoutdeparting from the scope and/or spirit of the disclosure. As such, allexamples and/or embodiments are deemed to be non-limiting throughoutthis disclosure.

Also, no inference should be drawn regarding those embodiments discussedherein relative to those not discussed herein other than it is as suchfor purposes of reducing space and repetition. For instance, it is to beunderstood that the logical and/or topological structure of anycombination of any program components (a component collection), othercomponents and/or any present feature sets as described in the figuresand/or throughout are not limited to a fixed operating order and/orarrangement, but rather, any disclosed order is exemplary and allequivalents, regardless of order, are contemplated by the disclosure.

Various concepts may be embodied as one or more methods, of which atleast one example has been provided. The acts performed as part of themethod may be ordered in any suitable way. Accordingly, embodiments maybe constructed in which acts are performed in an order different thanillustrated, which may include performing some acts simultaneously, eventhough shown as sequential acts in illustrative embodiments. Putdifferently, it is to be understood that such features may notnecessarily be limited to a particular order of execution, but rather,any number of threads, processes, services, servers, and/or the likethat may execute serially, asynchronously, concurrently, in parallel,simultaneously, synchronously, and/or the like in a manner consistentwith the disclosure. As such, some of these features may be mutuallycontradictory, in that they cannot be simultaneously present in a singleembodiment. Similarly, some features are applicable to one aspect of theinnovations, and inapplicable to others.

In addition, the disclosure may include other innovations not presentlydescribed. Applicant reserves all rights in such innovations, includingthe right to embodiment such innovations, file additional applications,continuations, continuations-in-part, divisionals, and/or the likethereof. As such, it should be understood that advantages, embodiments,examples, functional, features, logical, operational, organizational,structural, topological, and/or other aspects of the disclosure are notto be considered limitations on the disclosure as defined by theembodiments or limitations on equivalents to the embodiments. Dependingon the particular desires and/or characteristics of an individual and/orenterprise user, database configuration and/or relational model, datatype, data transmission and/or network framework, syntax structure,and/or the like, various embodiments of the technology disclosed hereinmay be implemented in a manner that enables a great deal of flexibilityand customization as described herein.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

As used herein, in particular embodiments, the terms “about” or“approximately” when preceding a numerical value indicates the valueplus or minus a range of 10%. Where a range of values is provided, it isunderstood that each intervening value, to the tenth of the unit of thelower limit unless the context clearly dictates otherwise, between theupper and lower limit of that range and any other stated or interveningvalue in that stated range is encompassed within the disclosure. Thatthe upper and lower limits of these smaller ranges can independently beincluded in the smaller ranges is also encompassed within thedisclosure, subject to any specifically excluded limit in the statedrange. Where the stated range includes one or both of the limits, rangesexcluding either or both of those included limits are also included inthe disclosure.

The indefinite articles “a” and “an,” as used herein in thespecification and in the embodiments, unless clearly indicated to thecontrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in theembodiments, should be understood to mean “either or both” of theelements so conjoined, i.e., elements that are conjunctively present insome cases and disjunctively present in other cases. Multiple elementslisted with “and/or” should be construed in the same fashion, i.e., “oneor more” of the elements so conjoined. Other elements may optionally bepresent other than the elements specifically identified by the “and/or”clause, whether related or unrelated to those elements specificallyidentified. Thus, as a non-limiting example, a reference to “A and/orB”, when used in conjunction with open-ended language such as“comprising” can refer, in one embodiment, to A only (optionallyincluding elements other than B); in another embodiment, to B only(optionally including elements other than A); in yet another embodiment,to both A and B (optionally including other elements); etc.

As used herein in the specification and in the embodiments, “or” shouldbe understood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as “only one of” or “exactly one of,” or, when usedin the embodiments, “consisting of,” will refer to the inclusion ofexactly one element of a number or list of elements. In general, theterm “or” as used herein shall only be interpreted as indicatingexclusive alternatives (i.e. “one or the other but not both”) whenpreceded by terms of exclusivity, such as “either,” “one of,” “only oneof,” or “exactly one of.” “Consisting essentially of,” when used in theembodiments, shall have its ordinary meaning as used in the field ofpatent law.

As used herein in the specification and in the embodiments, the phrase“at least one,” in reference to a list of one or more elements, shouldbe understood to mean at least one element selected from any one or moreof the elements in the list of elements, but not necessarily includingat least one of each and every element specifically listed within thelist of elements and not excluding any combinations of elements in thelist of elements. This definition also allows that elements mayoptionally be present other than the elements specifically identifiedwithin the list of elements to which the phrase “at least one” refers,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, “at least one of A and B” (or,equivalently, “at least one of A or B,” or, equivalently “at least oneof A and/or B”) can refer, in one embodiment, to at least one,optionally including more than one, A, with no B present (and optionallyincluding elements other than B); in another embodiment, to at leastone, optionally including more than one, B, with no A present (andoptionally including elements other than A); in yet another embodiment,to at least one, optionally including more than one, A, and at leastone, optionally including more than one, B (and optionally includingother elements); etc.

In the embodiments, as well as in the specification above, alltransitional phrases such as “comprising,” “including,” “carrying,”“having,” “containing,” “involving,” “holding,” “composed of,” and thelike are to be understood to be open-ended, i.e., to mean including butnot limited to. Only the transitional phrases “consisting of” and“consisting essentially of” shall be closed or semi-closed transitionalphrases, respectively, as set forth in the United States Patent OfficeManual of Patent Examining Procedures, Section 2111.03.

Some embodiments and/or methods described herein can be performed bysoftware (executed on hardware), hardware, or a combination thereof.Hardware modules may include, for example, a processor, a fieldprogrammable gate array (FPGA), and/or an application specificintegrated circuit (ASIC). Software modules (executed on hardware) caninclude instructions stored in a memory that is operably coupled to aprocessor, and can be expressed in a variety of software languages(e.g., computer code), including C, C++, Java®, Ruby™, Visual Basic™,and/or other object-oriented, procedural, or other programming languageand development tools. Examples of computer code include, but are notlimited to, micro-code or micro-instructions, machine instructions, suchas produced by a compiler, code used to produce a web service, and filescontaining higher-level instructions that are executed by a computerusing an interpreter. For example, embodiments may be implemented usingimperative programming languages (e.g., C, Fortran, etc.), functionalprogramming languages (Haskell, Erlang, etc.), logical programminglanguages (e.g., Prolog™), object-oriented programming languages (e.g.,Java®, C++, etc.) or other suitable programming languages and/ordevelopment tools. Additional examples of computer code include, but arenot limited to, control signals, encrypted code, and compressed code.

The term “processor” should be interpreted broadly to encompass ageneral purpose processor, a central processing unit (CPU), amicroprocessor, a digital signal processor (DSP), a controller, amicrocontroller, a state machine and so forth. Under some circumstances,a “processor” may refer to an application specific integrated circuit(ASIC), a programmable logic device (PLD), a field programmable gatearray (FPGA), etc. The term “processor” may refer to a combination ofprocessing devices, e.g., a combination of a DSP and a microprocessor, aplurality of microprocessors, one or more microprocessors in conjunctionwith a DSP core or any other such configuration.

The term “memory” should be interpreted broadly to encompass anyelectronic component capable of storing electronic information. The termmemory may refer to various types of processor-readable media such asrandom access memory (RAM), read-only memory (ROM), non-volatile randomaccess memory (NVRAM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasable PROM(EEPROM), flash memory, magnetic or optical data storage, registers,etc. Memory is said to be in electronic communication with a processorif the processor can read information from and/or write information tothe memory. Memory that is integral to a processor is in electroniccommunication with the processor.

The terms “instructions” and “code” should be interpreted broadly toinclude any type of computer-readable statement(s). For example, theterms “instructions” and “code” may refer to one or more programs,routines, sub-routines, functions, procedures, etc. “Instructions” and“code” may comprise a single computer-readable statement or manycomputer-readable statements.

While specific embodiments of the present disclosure have been outlinedabove, many alternatives, modifications, and variations will be apparentto those skilled in the art. Accordingly, the embodiments set forthherein are intended to be illustrative, not limiting. Various changesmay be made without departing from the spirit and scope of thedisclosure.

1. A computer-implemented method comprising: receiving, by a computingsystem, a signal associated with transmission of a first map update;determining, by the computing system, a first plurality of vehicles forthe first map update based on a map region associated with the first mapupdate; and transmitting, by the computing system, the first map updateto the first plurality of vehicles.
 2. The computer-implemented methodof claim 1, wherein the signal associated with transmission of the firstmap update includes an annotation generated by a first vehicle, whereinthe first plurality of vehicles does not include the first vehicle. 3.The computer-implemented method of claim 1, further comprising:transmitting, by the computing system, the map update to a secondplurality of vehicles subsequent to transmitting the map update to thefirst plurality of vehicles based on a determination the secondplurality of vehicles is further from the map region than the firstplurality of vehicles.
 4. The computer-implemented method of claim 1,further comprising: transmitting, by the computing system, a second mapupdate to a second plurality of vehicles based on a determination of asituation associated with the map region, wherein the second pluralityof vehicles is further from the map region than the first plurality ofvehicles.
 5. The computer-implemented method of claim 1, wherein thefirst plurality of vehicles for the map update is determined based on apriority list.
 6. The computer-implemented method of claim 1, whereinthe first plurality of vehicles for the map update is determined basedon a predetermined radius associated with the map region.
 7. Thecomputer-implemented method of claim 1, wherein the first plurality ofvehicles for the map update is determined based on a type of vehicleassociated with the first plurality of vehicles.
 8. Thecomputer-implemented method of claim 1, further comprising: preventing,by the computing system, the first plurality of vehicles from operatingin a mode of driving until the first map update has been used.
 9. Thecomputer-implemented method of claim 1, further comprising: providing,by the computing system, a notification associated with the transmittingthe first map update to the first plurality of vehicles.
 10. Thecomputer-implemented method of claim 1, further comprising: providing,by the computing system, an interface for verification of the mapupdate, wherein the transmitting the first map update to the firstplurality of vehicles is based on the verification.
 11. A systemcomprising: at least one processor; and a memory storing instructionsthat, when executed by the at least one processor, cause the system toperform operations comprising: receiving a signal associated withtransmission of a first map update; determining a first plurality ofvehicles for the first map update based on a map region associated withthe first map update; and transmitting the first map update to the firstplurality of vehicles.
 12. The system of claim 11, wherein the signalassociated with transmission of the first map update includes anannotation generated by a first vehicle, wherein the first plurality ofvehicles does not include the first vehicle.
 13. The system of claim 11,the operations further comprising: transmitting the map update to asecond plurality of vehicles subsequent to transmitting the map updateto the first plurality of vehicles based on a determination the secondplurality of vehicles is further from the map region than the firstplurality of vehicles.
 14. The system of claim 11, the operationsfurther comprising: transmitting a second map update to a secondplurality of vehicles based on a determination of a situation associatedwith the map region, wherein the second plurality of vehicles is furtherfrom the map region than the first plurality of vehicles.
 15. The systemof claim 11, wherein the first plurality of vehicles for the map updateis determined based on a priority list.
 16. A non-transitorycomputer-readable storage medium including instructions that, whenexecuted by at least on processor of a computing system, cause thecomputing system to perform operations comprising: receiving a signalassociated with transmission of a first map update; determining a firstplurality of vehicles for the first map update based on a map regionassociated with the first map update; and transmitting the first mapupdate to the first plurality of vehicles.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein the signalassociated with transmission of the first map update includes anannotation generated by a first vehicle, wherein the first plurality ofvehicles does not include the first vehicle.
 18. The non-transitorycomputer-readable storage medium of claim 16, the operations furthercomprising: transmitting the map update to a second plurality ofvehicles subsequent to transmitting the map update to the firstplurality of vehicles based on a determination the second plurality ofvehicles is further from the map region than the first plurality ofvehicles.
 19. The non-transitory computer-readable storage medium ofclaim 16, the operations further comprising: transmitting a second mapupdate to a second plurality of vehicles based on a determination of asituation associated with the map region, wherein the second pluralityof vehicles is further from the map region than the first plurality ofvehicles.
 20. The non-transitory computer-readable storage medium ofclaim 16, wherein the first plurality of vehicles for the map update isdetermined based on a priority list.